Reconciling the Needs of Architectural Description

Complex software systems require expressive notations fo their software architectures. Two competing paths have emerged. O specialized notation for architecture – or architecture description lan The other is to adapt a general-purpose modeling notation, such as U has a number of benefits, including familiarity to developers, close m plementations, and commercial tool support. However, it remains an as to how best to use object-oriented notations for architectural de indeed, whether they are sufficiently expressive, as currently defined we take a systematic look at these questions, examining the spa mappings from ADLs into object notations. Specifically, we de principle strategies for representing architectural structure in UML; ( and limitations of each strategy; and (c) aspects of architectural desc intrinsically difficult to model in UML using the strategies.